IRIX Base Documentation 2002 November

home *** CD-ROM | disk | FTP | other *** search

/ IRIX Base Documentation 2002 November / SGI IRIX Base Documentation 2002 November.iso / usr / share / catman / u_man / cat1 / psrip.z / psrip

Wrap

Text File | 2002-10-03 | 36.7 KB | 727 lines

PPPPSSSSRRRRIIIIPPPP((((1111)))) IIIImmmmpppprrrreeeessssssssaaaarrrriiiioooo PPPPSSSSRRRRIIIIPPPP((((1111)))) NNNNAAAAMMMMEEEE psrip - convert a PostScript file to raster data format SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS ppppssssrrrriiiipppp [----OOOO filename] [----LLLL filename] [----PPPP printer_name] [----FFFF format] [----BBBB bits] [----CCCC colorspace] [----dddd device_type[arg1,[arg2]]] [----WWWW width] [----HHHH height] [----RRRR res] [----XXXX hres] [----YYYY vres] [----UUUU hoff] [----VVVV voff] [----IIII filename] [----GGGG arg1,[arg2,[arg3,[arg4]]] [----TTTT] [----jjjj pixels] [----ffff] [----rrrr angle] [----llll] [----kkkk] [----vvvv] [----MMMM] [----SSSS] [----gggg scratch_dir] [----yyyy persistent_dir] [----aaaa startup_path] [----bbbb backend_path] [----cccc resource_path] [----oooo backend option] [----xxxx] [----hhhh] [----DDDD[[[[[[[[DDDD]]]]DDDD]]]]] [PostScript input file] DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN _p_s_r_i_p is a PostScript Level 2 interpreter with Adobe CPSI. _p_s_r_i_p converts a PostScript file into TIFF compatible raster output for use by printer drivers. This program supersedes the _p_s_r_i_p level 1 program which used Display Postscript. CCCCoooommmmmmmmaaaannnndddd LLLLiiiinnnneeee OOOOppppttttiiiioooonnnnssss By default, _p_s_r_i_p assumes that its input will be arriving on the standard input, its output should be written to the standard output and error messages should be written to the standard error. If a filename is specified after all option switches, data will be read from that file rather than from the standard input. ----OOOO _f_i_l_e_n_a_m_e Specifies the name of the file to which the rasterized output will be sent. If the ----OOOO option is not specified, output will be sent to the standard output. ----LLLL _f_i_l_e_n_a_m_e Specifies the name of the file to which error, warning and informational messages are to be written. If the file specified already exists, any messages generated by _p_s_r_i_p will be appended to the end of the file. If the ----LLLL option is not specified, message output will be sent to standard error. ----PPPP _p_r_i_n_t_e_r__n_a_m_e Specifies the name of the printer for which raster output is to be generated. _p_r_i_n_t_e_r__n_a_m_e is the name of a printer that is physically attached to the system running _p_s_r_i_p. The printer name is used to locate the Printer Object Database (POD) for the printer (see _l_i_b_p_o_d(_3)). If this option is specified, the printer specific values for output width, length, and resolution are filled in from the POD and need not be specified using command-line options. Use of the ----PPPP option is preferable PPPPaaaaggggeeee 1111 PPPPSSSSRRRRIIIIPPPP((((1111)))) IIIImmmmpppprrrreeeessssssssaaaarrrriiiioooo PPPPSSSSRRRRIIIIPPPP((((1111)))) to manually setting the options because changes to the printer configuration file will then be reflected in the program's output. The values read from the POD file can be selectively overridden using the command-line options. If POD values must be overridden, specify the overriding options after (to the right of) the ----PPPP option, since the rightmost option takes precedence. For compatibility with previous releases of the _I_m_p_r_e_s_s_a_r_i_o product, the ----PPPP option can take a full pathname to the POD files instead of a printer name. _p_s_r_i_p automatically detects that a complete pathname has been specified and looks for the POD files in the directory specified by that pathname. The use of full POD pathnames is discouraged. ----FFFF _f_o_r_m_a_t Specifies the output raster data format. _f_o_r_m_a_t may be specified as cccchhhhuuuunnnnkkkkyyyy, or the default, ppppllllaaaannnnaaaarrrr. The data format is normally derived from the POD (see ----PPPP), which is kept up to date with the current printer configuration. Chunky data is organized such that the color values for each dot appear together. For example, if a dot consists of three colors C, M and Y, chunky output format for a 3 dot by 3 dot image would be organized as: CMYCMYCMY CMYCMYCMY CMYCMYCMY Note that for the case of one bit per component, the chunky data above would contain a trailing 0 to nibble align each pixel's data (i.e. CMY0CMY0CMY0). Depths greater than one bit per component pack the data (i.e. CMYCMYCMY). Planar data is organized such that all data for one color component is output followed by all data for the next color component and so on. For example, the CMY data in the above example organized for planar output would appear as: CCC CCC CCC MMM MMM MMM YYY YYY YYY PPPPaaaaggggeeee 2222 PPPPSSSSRRRRIIIIPPPP((((1111)))) IIIImmmmpppprrrreeeessssssssaaaarrrriiiioooo PPPPSSSSRRRRIIIIPPPP((((1111)))) The selection of output data organization for single component colorspaces is moot. Therefore, when the kkkk or wwww colorspace is specified, the ----FFFF switch is ignored and by convention the output is considered to be in cccchhhhuuuunnnnkkkkyyyy format. ----BBBB _b_i_t_s Specifies the number of bits per color component for the output data. Currently, _b_i_t_s may be specified as 1111, the default, 4444, or 8888. The bits per color is normally derived from the POD (see ----PPPP), which is kept up to date with the current printer configuration. ----CCCC _c_o_l_o_r_s_p_a_c_e Specifies the output data colorspace. The standard values of _c_o_l_o_r_s_p_a_c_e may be one of the following: kkkk, the default, wwww (inverse k), ccccmmmmyyyy, ccccmmmmyyyykkkk, yyyymmmmcccc, yyyymmmmcccckkkk, kkkkccccmmmmyyyy, or rrrrggggbbbb. These values will all produce TIFF compatible output organized according to the ----FFFF option with a depth per color component specified by the ----BBBB option. ----ZZZZ _c_o_m_p_r_e_s_s_i_o_n Specifies the compression scheme to be used on the output data. Currently, compression is not supported. ----WWWW _w_i_d_t_h, ----HHHH _h_e_i_g_h_t The ----WWWW and ----HHHH options specify the output data area in dots, in the horizontal (width) and vertical (height) directions, respectively. These values are normally derived from the POD (see ----PPPP), which is kept up to date with the currently loaded paper size. The default width and height correspond to an 8.5 by 11 inch output area rendered at 100 dots per inch (dpi). Therefore, the default output area is: default width = 850 dots default height = 1100 dots ----RRRR _r_e_s, ----XXXX _h_r_e_s, ----YYYY _v_r_e_s The ----RRRR option specifies the printer resolution in dots per inch in the horizontal (width) and vertical (height) directions simultaneously. These values may be set independently using the ----XXXX (for width) and ----YYYY (for height) options. These values are normally derived from the POD (see ----PPPP), which is kept up to date with the current printer configuration. The default horizontal and vertical resolutions are 100 dots per inch. There is no maximum resolution limitation. ----UUUU _h_o_f_f, ----VVVV _v_o_f_f These options specify the horizontal (x) and vertical (y) offsets of the frame buffer origin in dots, respectively. These options may be used to adjust the PostScript origin to compensate for image clipping and should be used with care. The default horizontal and vertical offsets are zero. Note that PPPPaaaaggggeeee 3333 PPPPSSSSRRRRIIIIPPPP((((1111)))) IIIImmmmpppprrrreeeessssssssaaaarrrriiiioooo PPPPSSSSRRRRIIIIPPPP((((1111)))) these offset are relative to the page and are not effected by image rotation or flipping. ----IIII _f_i_l_e_n_a_m_e It is often necessary to prepend PostScript code onto a PostScript file before it can be properly interpreted. Typically this prolog code consists of PostScript functions and definitions that will be referenced by the main PostScript file. Often the prolog is concatenated onto the beginning of the main file and the result is interpreted as a single file. The _p_s_r_i_p program provides a more efficient means for prepending prolog files. The ----IIII flag allows a prolog file to be included for processing before the main PostScript file. Multiple ----IIII flags can be specified on the command-line. The files will be processed from left to right in the order specified. ----TTTT At present this option performs no function in the level 2 rip. There is a default screen installed with the rip which can only be overridden by Postscript screen/halftone commands. It is not clear what purpose, if any, this option may perform in the future. Since halftoning is a device dependent operation the default halftone may not produce adequate results on certain output devices. Under these circumstances it may be necessary to define a new PostScript halftone cell and prepend this definition to the input file as a PostScript prolog. Please refer to the "_P_o_s_t_S_c_r_i_p_t _L_a_n_g_u_a_g_e _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l" for information on halftone cells. Refer to the ----IIII switch for information on prolog files. ----GGGG _r_e_d__g_a_m_m_a,[_g_r_e_e_n__g_a_m_m_a,[_b_l_u_e__g_a_m_m_a,[_g_r_a_y__g_a_m_m_a]]] Specifies gamma values that will be applied before the current job is executed. This option is realized via the Postscript setcolortransfer operator. The red_gamma is applied to the red/cyan color plane, the green_gamma is applied to the green/magenta color plane, the blue_gamma is applied to the blue/yellow color plane, and the gray_gamma to any black or gray color plane. The default value, no gamma correction (1.0), will be applied to any planes which are not specified via the command line. Please note that one must specify all the gamma values to specify a gray gamma value. Each gamma value is interpreted as a floating point number. ----ffff Specifies that the output image should be flipped (mirrored) about the vertical axis. This flag is useful when creating transparencies. Note that flipping of the image is performed after any rotation. Therefore, the image is always flipped about the vertical axis. PPPPaaaaggggeeee 4444 PPPPSSSSRRRRIIIIPPPP((((1111)))) IIIImmmmpppprrrreeeessssssssaaaarrrriiiioooo PPPPSSSSRRRRIIIIPPPP((((1111)))) ----rrrr _a_n_g_l_e Specifies that the image is to be rotated by _a_n_g_l_e degrees. Positive rotations are counter-clockwise measured from the horizontal axis. The default rotation angle is 0. _a_n_g_l_e may be any positive or negative integer. Only angles which are a multiple of 90 degrees are supported. Specified angles that are not multiples of 90 degrees are snapped to the nearest multiple of 90 degrees. ----llll Specifies that the output should be in landscape orientation rather than portrait. Note that specifying this option simply creates the raster imaging framebuffer with the page width and height values swapped. It is the responsibility of the PostScript input code to operate correctly in a landscape orientation. It may be necessary to specify an image rotation using the ----rrrr switch and a frame buffer offset using the ----UUUU and ----VVVV switches in order to obtain the desired landscape results. ----MMMM The psrip program has two methods for allocating raster buffer storage. The back end DSO must define raster buffer allocation and deallocation functions that are used as callbacks by CPSI for raster buffer memory management. If the ----MMMM option is specified raster buffer allocation will be made by memory mapping a temporary disk file. This tends to improve performance when a large frame device is used (see the ----dddd option). The ----MMMM option only takes effect when the device type is a frame device. The temporary file is created in the interpreter scratch file directory (see the ----gggg option). The size of the temporary file will be equal to the amount of storage required for the raster buffer rounded up to the nearest memory page. For a frame device this can lead to a very large file. The temporary file is automatically removed by psrip. ----SSSS A standard PostScript document will use a sssshhhhoooowwwwppppaaaaggggeeee operator between each page. The sssshhhhoooowwwwppppaaaaggggeeee operator instructs the interpreter to output the current raster image. Typically, Encapsulated PostScript files do not contain a sssshhhhoooowwwwppppaaaaggggeeee operator. The ----SSSS switch forces the execution of a sssshhhhoooowwwwppppaaaaggggeeee operator at the end of the PostScript file if a sssshhhhoooowwwwppppaaaaggggeeee has never been issued by the file. If the file has issued a sssshhhhoooowwwwppppaaaaggggeeee this switch has no effect. If a syntactically correct PostScript file does not produce an output image, the ----SSSS flag may be specified to force a single page output. ----dddd ddddeeeevvvviiiicccceeeeTTTTyyyyppppeeee[[[[,,,,aaaarrrrgggg1111[[[[,,,,aaaarrrrgggg2222]]]]]]]] Specifies how raster image data should be fed from the interpreter kernel to the back end DSO. The available values of deviceType are described below. The default device type is auto. Note that certain values of deviceType accept optional arguments (i.e. arg1 and arg2). PPPPaaaaggggeeee 5555 PPPPSSSSRRRRIIIIPPPP((((1111)))) IIIImmmmpppprrrreeeessssssssaaaarrrriiiioooo PPPPSSSSRRRRIIIIPPPP((((1111)))) _n_u_l_l Specifies that no raster image is to be produced. No raster buffer storage is allocated and the show, stroke, show page and copypage operators do nothing. However, all other aspects of interpreting the page description proceed normally. The best use of this option is to check a PostScript page description for syntactical or resource allocation errors, so called preflighting. _f_r_a_m_e Specifies that a frame device should be used for imaging. A frame device allocates storage for a complete raster output page. The frame device was the only device type available in the Level 1 psrip. _b_a_n_d[,_n_u_m_B_u_f_f_e_r_s[,_m_e_m_L_i_m_i_t]] Specifies that a band device be used. A band device renders the output raster image as a series of sequential bands and thus can use considerably less memory than a frame device. The back end is passed bands as they are rendered. The RIP can do a certain amount of parallel processing of bands and so the numBuffers option can specify the number of band buffers to be used. The default number of buffers is 1. The number of raster lines per band is determined by the memLimit option. This option specifies the total amount of memory that may be used for all band buffers. The default memory limit is 5 MBytes. memLimit is specified in number of bytes. Since the number of scan line in a band must be a power of two, the actual memory used for band buffers may differ from the specified memory limit. _a_u_t_o[,_n_u_m_B_u_f_f_e_r_s[,_m_e_m_L_i_m_i_t]] Specifies that psrip should decide whether to use a frame device or a band device. This is the default device type. The decision is made based on the number of buffers to be used, numBuffers, and the memory use limit, memLimit. The RIP starts by assuming a frame device and calculates the amount of memory required. If the total amount of memory required exceeds memLimit, a band device is used. The band device is created with numBuffers bands and a total memory limit of memLimit. The default numBuffers is 1 and the default memLimit is 5 megabytes. The syntax for memLimit is the number of bytes. Since the number of scan lines in a band must be a power of two, the actual memory used for band buffers may differ from the specified memory limit. The 5 megabyte default memory limit was chosen because it is enough to render an 8.5 by 11 inch page with 1-bit per color CMYK at 300 dpi using a frame device. PPPPaaaaggggeeee 6666 PPPPSSSSRRRRIIIIPPPP((((1111)))) IIIImmmmpppprrrreeeessssssssaaaarrrriiiioooo PPPPSSSSRRRRIIIIPPPP((((1111)))) ----gggg _s_c_r_a_t_c_h_D_i_r During execution the interpreter creates a scratch directory to place a number of temporary files. The directory and its contents are removed upon termination of _p_s_r_i_p. The ----gggg option specifies the directory in which the scratch directory is to be created. The directory specified with the ----gggg option must exist and is not created (scratch directories within the specified directory are created). For example, if scratchDir is /usr/foodir then psrip will create the scratch directory /usr/foodir/uniqueDirName and place all temporary files in the /usr/foodir/uniqueDirName directory. The directory uniqueDirName and its contents will be removed by _p_s_r_i_p upon termination. If the ----gggg option is not specified, the default scratch file directory is created in one of two locations. If the environment variable PSRIPTMPDIR specifies a directory, the scratch directory will be created in that directory/<uniqueDirName>. If the variable is not set, the directory will be created in the /var/spool/lp/psparams/<uniqueDirName> directory. The uniqueDirName is created in all cases. This is necessary as all instances of the interpreter must have individual scratch areas. ----yyyy _p_e_r_s_i_s_t_e_n_t_D_i_r The interpreter kernel caches persistent configuration information in a number of disk files. The ----yyyy option can be used to specify an alternate persistent directory. The directory specifed with the ----yyyy option must exist (_p_s_r_i_p will not create it). Persistent information is used by the interpreter across invocations. For example, the total number of pages output by the RIP (the PageCount parameter) is maintained in a persistent file. By default persistent files are created by the interpreter in one of two directories. If a printer name has been specified (see ----PPPP option) and psrip is being run as the lp user (based on euid), the persistent files will be created in the directory /var/spool/lp/psparams/<printerName>. If a printer has not been specified or the user is not lp, the persistent files will be created in the scratch file directory (see ----gggg option) and will be removed upon termination of the RIP. If the ----yyyy option is specified, persistentfiles will be placed in the directory persistentDir regardless of the user and regardless of whether a printer has been specified. ----aaaa _s_t_a_r_t_u_p_P_a_t_h Specifies a search path for the directory containing the startup.ps code and the POSTSCRIPT.VM initial VM file. The search path is a colon separated list of directories. The path is searched until each file is found. The default search path is /usr/lib/print/data/psrip. If startupPath contains a path PPPPaaaaggggeeee 7777 PPPPSSSSRRRRIIIIPPPP((((1111)))) IIIImmmmpppprrrreeeessssssssaaaarrrriiiioooo PPPPSSSSRRRRIIIIPPPP((((1111)))) consisting of the single character %, the default path will be substituted. For example, if startupPath is specified as %:/usr/people/foo the startup file search path will be /usr/lib/print/data/psrip:/usr/people/foo. ----bbbb _b_a_c_k_e_n_d_P_a_t_h Specifies a search path for back end DSOs. All directories long the path are searched until the required DSO is found. A back end DSO is identified by a file ending in .so. The search path is a colon separated list of directories. The default search path is /usr/lib/print/psdevdso. If back endPath contains a path consisting of the single character %, the default path will be substituted. For example, if backendPath is specified as %:/ usr/people/foo the back end DSO search path will be /usr/lib/print/ psdevdso:/usr/people/foo. If DSOs along the search path have the same name, the first DSO encountered will be used. ----cccc _r_e_s_o_u_r_c_e_P_a_t_h Specifies a search path for interpreter resource files. All directories along the path are searched for files ending in .upr. The search path is a colon separated list of directories. The default search path is /usr/lib/print/data/psrip. If resourcePath contains a path consist ing of the single character %, the default path will be substituted. For example, if resourcePath is specified as %:/usr/people/foo the resource file search path will be /usr/lib/print/data/psrip:/usr/people/foo. Printer-specific resource files can be read by adding their directory to resourcePath. ----oooo _b_a_c_k_e_n_d_O_p_t_i_o_n_s This option is used to specify a string which will be passed to the backend active during processing. The contents of the backend option string is backend dependent. Basically, this establishes a method of communication between the psrip user and the backend. ----kkkk Normally, psrip outputs the raster image with the PostScript origin on the trailing scan edge of the image. That is the origin is on the last raster line of the image. The ----kkkk option place the origin along the leading raster line. This option is equivalent to the option ----rrrr _1_8_0. ----vvvv This option is used to color invert the output image. For example, inverting an rgb image results in the red, green and blue components replaced by cyan, magenta and yellow PPPPaaaaggggeeee 8888 PPPPSSSSRRRRIIIIPPPP((((1111)))) IIIImmmmpppprrrreeeessssssssaaaarrrriiiioooo PPPPSSSSRRRRIIIIPPPP((((1111)))) respectively. ----jjjj _p_i_x_e_l_s This option is used with xerographic engines. For a xerographic marking engine, laser light illuminates spots on a photosensitive medium that correspond to pixels of the raster image. Different technologies illuminate either the spots that correspond to colored pixels in the raster image - write-black engines - or else illuminate the spots that correspond to uncolored (white or blank) pixels in the raster image - write- white engines. This option is for use with write-white engines. The shapes of pixel marks on the medium are sufficiently different between write-black and write-white marking engines that special compensation must be made for the thinner shapes produced by write-white engines. The pixels argument specifies the number of pixels by which to fatten zero-width (one pixel) lines so that they do not break up on write- white marking engines. Specifying this option with a non-zero value of pixels also disables both the ATM font rasterizer and Type 1 hinting. Therefore, this option should only be used on write-white marking engines for which the rendering artifacts are quite pronounced and unsatisfactory. ----xxxx Specifies that psrip should run in executive (i.e. interactive) mode. When run in this mode, the interpreter processes all startup code but ignores any input page description file. The interpreter accepts Post Script input at the PS> prompt. To exit the interpreter type CTRL-D or quit. In order to capture raster output the ----OOOO option must be specified. If ----OOOO is not specified all raster output is sent to stdout. ----EEEE The ----EEEE switch, which provided backwards compatibility with the pschunky program, has been removed. ----hhhh Prints a program usage message to the standard error. This usage message also lists the currently supported output configurations. ----DDDD[[[[DDDD[[[[DDDD]]]]]]]] Specifies verbose output for debugging purposes. There are three levels of debugging information available. WWWWAAAARRRRNNNNIIIINNNNGGGGSSSS 1. The CHUNKY output formats _o_l_d_k, _o_l_d_c_m_y, and _o_l_d_c_m_y_k previously provided by _p_s_r_i_p for compatibility with previous releases of the _I_m_p_r_e_s_s_a_r_i_o product have been removed. 2. By default _p_s_r_i_p allocates memory for one complete output page. This means that very large and/or high resolution output images require a large amount of system memory. It is possible to specify an output image that exceeds the virtual memory system's available memory swap PPPPaaaaggggeeee 9999 PPPPSSSSRRRRIIIIPPPP((((1111)))) IIIImmmmpppprrrreeeessssssssaaaarrrriiiioooo PPPPSSSSRRRRIIIIPPPP((((1111)))) space. Refer to the _s_w_a_p(1M) man page for information on adjusting system swap space. Please note that the ----dddd option can be used to invoke the interpreter in banding mode. This eliminates the memory limitations resulting from large output images. 3. Under IRIX 5.2 there is a process size limit of 512 MBytes. The process size limit can be increased by adjusting the values of the _r_l_i_m_i_t parameters in the IRIX kernel configuration file /_v_a_r/_s_y_s_g_e_n/_m_t_u_n_e/_k_e_r_n_e_l. Note that for a new kernel configuration to take effect a new kernel must be built using the _a_u_t_o_c_o_n_f_i_g(1M) program (the -_f switch must be specified). See the _m_t_u_n_e(4) and _a_u_t_o_c_o_n_f_i_g(1M) man pages for reconfiguring and building a new IRIX kernel. NNNNOOOOTTTTEEEESSSS 1. The _p_s_r_i_p output file format is a TIFF compatible format called Stream TIFF (STIFF). STIFF is a dialect of TIFF that can be read from or written to non-seekable streams. The _p_s_r_i_p program will write a printing specific form of STIFF. Refer to the _l_i_b_s_t_i_f_f(_3) manual page for detailed information on the STIFF file format. 2. If _p_s_r_i_p is given an unrecognized or incomplete command line option switch, it will print an error message to the standard error and terminate the program. This differs from previous versions which issued a warning and attempted to continue. 3. The level 2 _p_s_r_i_p ignores CCCCTTTTRRRRLLLL----DDDD and CCCCTTTTRRRRLLLL----ZZZZ characters in the postscript data stream. A warning message indicating that one of the above characters has been processed is logged, but no action is taken. 4. The level 2 _p_s_r_i_p when invoked from _I_m_p_r_e_s_s_a_r_i_o product runs with the user ID of "lp". Using the postscript file system it is possible to access files, for reading and/or writing, which may otherwise be inaccessible to any user other than "lp". 5. The level 2 _p_s_r_i_p contains a limit on image content. This image content is defined as follows: Image Content = (Resolution * Bits Per Pixel * Number of Color Planes) / 8 Please note that the resolution represents the maximum of the x and y resolutions. If the image content exceeds 600, _p_s_r_i_p will fail and the program will terminate. At present, it is not possible to acquire the license necessary to relax this restriction. See the Impressario Programming Guide for additional information. PPPPaaaaggggeeee 11110000 PPPPSSSSRRRRIIIIPPPP((((1111)))) IIIImmmmpppprrrreeeessssssssaaaarrrriiiioooo PPPPSSSSRRRRIIIIPPPP((((1111)))) FILES /usr/lib/print/psrip Program file /usr/lib/print/data/psrip/Postscript.VM Postscript VM file /usr/lib/print/data/psrip/startup.ps Startup code /usr/lib/print/data/psrip PostScript resource directory (fonts, CRDs, etc.) /usr/lib/print/psdevdso Default directory containing backend DSOs. /var/spool/lp/psparams Default base directory for persistent parameters and scratch files. TTTTRRRRAAAADDDDEEEEMMMMAAAARRRRKKKKSSSS PostScript is a registered trademark of Adobe Systems, Inc. Apple and LaserWriter are registered trademarks of Apple Computer, Inc. SSSSEEEEEEEE AAAALLLLSSSSOOOO sgi2ps(1), stiff2ps(1), libstiff(3), libpod(3), _P_o_s_t_S_c_r_i_p_t _L_a_n_g_u_a_g_e _R_e_f_e_r_e_n_c_e _M_a_n_u_a_l - 2nd ed., Adobe Systems, Inc. PPPPaaaaggggeeee 11111111